Skip to content
This repository has been archived by the owner on Nov 30, 2021. It is now read-only.

Release 1.0.0 #55

Merged
merged 80 commits into from
Feb 18, 2021
Merged

Release 1.0.0 #55

merged 80 commits into from
Feb 18, 2021

Conversation

dvvanessastoiber
Copy link
Collaborator

Release notes

Checklists

Release preparation

  • Create new release-x.x.x branch (based on develop branch)
  • Collect changes and write release notes
  • Draft release PR in GitHub that merges the release-x.x.x into the master branch

Release dependencies first

In case of dependent Phovea/TDP repositories follow dependency tree from the top:

  • Release dependent repositories if they contain changes first before proceeding here
  • Replace git dependencies in package.json with new version range (e.g., "phovea_core": "^2.3.1" when published on npm or "phovea_core": "github:datavisyn/tdp_core#semver:^8.0.0" for non-published repositories)
  • Commit and push new dependencies
  • Wait until build is successful
  • Repeat with other repositories/dependencies or proceed with next section

Update version

  • Check version numbers of dependencies again
  • Check if build is successful
  • Update this version number following semver
  • Commit and push package.json with new version number
  • Assign reviewer and wait for final review
  • Merge this pull request into master branch
  • Add release label (i.e., release: major, release: minor, or release: patch)

Publish npm release

The steps of this section are only necessary if the code is public and should be published to the npm registry.

  • chmod -R o+w . in the cloned repository directory (to provide write access to the CircleCI Linux user)
  • rm -rf dist && rm -rf build && rm -rf node_modules/ && rm -rf package-lock.json
  • docker run -it -v $(pwd):/phovea circleci/node:12.13-buster-browsers /bin/bash and continue inside the container
  • cd /phovea
  • npm install
  • npm run build to build the bundles
  • npm login as caleydo-bot
  • npm publish
  • Check release on npmjs.com

Create GitHub release

  • Draft a new release (Code -> Releases -> Draft a new release)
  • Use new version number as tag (e.g., v2.3.1)
  • Copy release notes
  • Publish release

Prepeare next develop release

  • Switch to develop branch
  • Merge master branch into develop (git merge origin/master)
  • Update version in package.json to <next patch version>-SNAPSHOT (e.g., 2.3.1 to 2.3.2-SNAPSHOT)
  • Revert dependencies in package.json to develop branches (e.g., "phovea_core": "github:phovea/phovea_core#develop")
  • Commit and push changes

🏁 Finish line

  • Inform colleagues and customers about the release
  • Celebrate the new release 🥳

rumersdorfer and others added 30 commits December 18, 2019 22:55
*  Add TS compiler flags for i18n to tsconfig.json

* Update template files and dependencies

Using generator-phovea v3.0.0

- Update CircleCI config
- Update tslint.json

* Update package-lock.json

* Invalidate circleci cache

* Fix tslint

* Update package-lock.json

* Invalidate circleci cache

* Fix several tslint errors

* Invalidate circleci cache

* Force npm install

* Revert circleci config

* Force npm install

* Install clue explicitly

* Revert install phovea_clue explicitly

* Invalidate circleci cache

* Remove explicit phovea_core dependency
Remove and ignore package-lock.json
add CODEOWNERS file
older version uses typescript 2 as peerDependency
@dvvanessastoiber dvvanessastoiber added the release: major PR merge results in a new major version label Feb 18, 2021
@thinkh thinkh merged commit 988c2a1 into master Feb 18, 2021
@thinkh thinkh deleted the release-1.0.0 branch February 18, 2021 09:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release: major PR merge results in a new major version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add login and provenance menu to header
4 participants